Probably Array should be allowed too (for ints).

about this closing #60516, there's still the wider issue of @export_* annoations in general having no support for arrays.

for instance, an user may want to export arrays of file paths, bit flags, or ranges just as well.

@export_multiline is currently the sole annotation that already supports arrays, as this is valid: @export_multiline var my_multiline: Array[String].

although if it makes more sense for #60516 to pertain to @export_enum exclusively, I'll change back its title to the original. 🙂

for reference, here's a snippet that can be used to quickly test the array support of all @export_* annoations:

@export_dir var my_dir: Array[String]
@export_file var my_file: Array[String]
@export_global_dir var my_global_dir: Array[String]
@export_global_file var my_global_file: Array[String]
@export_enum("A", "B", "C") var my_enum_str: Array[String]
@export_enum("A", "B", "C") var my_enum_int: Array[int]
@export_flags("A", "B", "C") var my_bit_flag: Array[int]
@export_flags_2d_navigation var my_bit_flag_2d_nav: Array[int]
@export_flags_2d_physics var my_bit_flag_2d_phys: Array[int]
@export_flags_2d_render var my_bit_flag_2d_render: Array[int]
@export_flags_3d_navigation var my_bit_flag_3d_nav: Array[int]
@export_flags_3d_physics var my_bit_flag_3d_phys: Array[int]
@export_flags_3d_render var my_bit_flag_3d_render: Array[int]
@export_multiline var my_multiline: Array[String]
@export_placeholder("Placeholder") var my_placeholder: Array[String]
@export_range(1, 10) var my_range_int: Array[int]
@export_range(1.0, 10.0) var my_range_float: Array[float]
@export_exp_easing var my_exp_easing: Array[float]
@export_node_path var my_node_path: Array[NodePath]
@export_color_no_alpha var my_color: Array[Color]

See #72912. I'm not sure if we should support all valid combinations of export flags.

I opened this PR because this feature is in 3.x but not in 4.0. This looks like an obvious oversight, because this feature is documented in 3.x, but in other cases it is not so obvious.

Perhaps you are right, and other export annotations should also support arrays.

ah, cool.
although if I understand correctly, @export_custom doesn't add functionality that isn't already achievable with _get_property_list(), no? seems more of an alternative syntax to _get_property_list(), while still not fully replacing it as you cannot add custom logic.

so if I wanted to, say, have an array of PROPERTY_HINT_COLOR_NO_ALPHA appear in the inspector, @export_custom would not help with that.

but I understand that only the missing array support for @export_enum is actually a regression, so #60516 should probably stick to that scope.

Yes, @export_custom is an "alternative syntax" of _get_property_list(), just like any export annotation. The difference is that this only takes one line and does not require @tool.

You could use @export_custom for this, it's just less convenient (I didn't check if it works):

@export_custom(PROPERTY_HINT_TYPE_STRING, "%s/%s:" % [TYPE_COLOR, PROPERTY_HINT_COLOR_NO_ALPHA])
var array: Array[Color]

But I think other export annotations should also support arrays, thanks for pointing that out. I'll try to expand this PR later or open a separate one (I think it won't require a lot of code). But keep in mind that this will not be included in 4.0.0 anyway.

• Superseded by Allow @exported Arrays to set property hints for their elements #82952.